in_mqtt: added buffer size setting and fixed a leak#9163
Merged
Conversation
Signed-off-by: Leonardo Alminana <leonardo.alminana@chronosphere.io>
leonardo-albertovich
requested review from
edsiper,
fujimotos and
koleini
as code owners
edsiper
requested changes
Aug 5, 2024
Signed-off-by: Leonardo Alminana <leonardo.alminana@chronosphere.io>
scne59
pushed a commit
to scne59/fluent-bit
that referenced
this pull request
Apr 9, 2025
--------- Signed-off-by: Leonardo Alminana <leonardo.alminana@chronosphere.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds an optional setting to the MQTT input plugin named
buffer_sizewhich sets the maximum message size.According to the MQTT standard the protocol can handle messages of up to 256 megabytes, however, to keep the default memory footprint low, the default value has been raised to 2048 bytes (from 1024 bytes).
Additionally, this PR fixes a leak in the protocol handler which triggered when a message did not contain a valid JSON payload.